Systems and methods for signaling in an increased carrier monitoring wireless communication environment

ABSTRACT

Systems and methods for signaling in an increased carrier monitoring wireless communication environment are disclosed herein. A user equipment (UE) may include control circuitry to configure the UE for increased carrier monitoring; determine, based on a first signal received from a network apparatus, whether a reduced performance group carrier is configured; determine, based on a second signal received from the network apparatus, whether a scaling factor is configured; and in response to a determination that no reduced performance group carrier is configured and a determination that no scaling factor is configured, allow the UE to monitor fewer carriers than required by increased carrier monitoring. Other embodiments may be disclosed and/or claimed.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/902,845, filed Feb. 22, 2018, entitled “SYSTEMS AND METHODS FORSIGNALING IN AN INCREASED CARRIER MONITORING WIRELESS COMMUNICATIONENVIRONMENT,” which is a continuation of U.S. application Ser. No.15/694,617, filed Sep. 1, 2017, entitled “SYSTEMS AND METHODS FORSIGNALING IN AN INCREASED CARRIER MONITORING WIRELESS COMMUNICATIONENVIRONMENT,” now U.S. Pat. No. 9,942,023, which is a continuation ofU.S. application Ser. No. 15/452,153, filed Mar. 7, 2017, entitled“SYSTEMS AND METHODS FOR SIGNALING IN AN INCREASED CARRIER MONITORINGWIRELESS COMMUNICATION ENVIRONMENT,” now U.S. Pat. No. 9,800,395, whichis a continuation of U.S. patent application Ser. No. 14/704,848, filedMay 5, 2015 now U.S. Pat. No. 9,635,574, which claims the benefit ofU.S. Provisional Application No. 62/082,004, filed Nov. 19, 2014,entitled “INCMON FEATURE UE BEHAVIOUR,” the content and disclosures ofeach of which are hereby incorporated by reference in their entireties.

FIELD

Embodiments of the present disclosure generally relate to the field ofwireless communication, and more particularly, to systems and methodsfor signaling in an increased carrier monitoring wireless communicationenvironment.

BACKGROUND

Some wireless communication protocols require user equipment to measurea certain number of carriers, and newer protocols may require some userequipment to measure more carriers than were required by olderprotocols. For example, a user equipment (UE) in a Release 11 Long TermEvolution (LTE) environment may be required to monitor only threeUniversal Terrestrial Radio Access (UTRA) frequency division duplex(FDD) carriers, while a user equipment in a Release 12 LTE environmentmay be required to monitor at least six UTRA FDD carriers.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example and not by wayof limitation in the figures of the accompanying drawings.

FIG. 1 is a block diagram of a portion of a wireless communicationenvironment in accordance with various embodiments.

FIG. 2 is a flow diagram of a process for operating a UE in accordancewith some embodiments.

FIG. 3 is a flow diagram of a process for operating a UE in accordancewith some embodiments.

FIG. 4 is a flow diagram of a process for operating an eNB in accordancewith some embodiments.

FIG. 5 is a block diagram of an example system that may be used topractice various embodiments described herein.

DETAILED DESCRIPTION

Embodiments of the present disclosure include systems and methods forsignaling in an increased carrier monitoring environment. A userequipment (UE) (such as a smartphone or other mobile communicationsdevice) may interact with many different types of wireless communicationnetworks as it moves through time and space. As new functions (such asincreased carrier monitoring, discussed below) are included in newernetwork specifications, a UE configured to perform such new functionsmay find the functions not recognized or otherwise not supported byolder or different network specifications. If the older or differentnetwork specifications did not anticipate the newer functions, a UEinteracting with such an older or different network may not receive thenetwork signals regarding the functions that it expects to receive, andtherefore may not know whether or not to perform the functions. Addingadditional function-specific signaling between the newer network and theUE may help address the ambiguity, but at the cost of additionalsignaling overhead. As wireless communication network specificationscontinue to be refined to be as lean and efficient with communicationresources as possible, such additional cost may be unacceptable.

Various ones of the embodiments disclosed herein may address theseissues by configuring UEs and the network components with which theyinteract (e.g., an eNB) to utilize particular combinations of existingsignaled data to communicate whether or not a UE should or should notfollow the requirements of increased carrier monitoring. Theseembodiments may mitigate or eliminate situations in which a UE hasunclear or conflicting instructions on whether or not increased carriermonitoring should be performed while incurring no or minimal signalingoverhead.

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof wherein like numeralsdesignate like parts throughout, and in which is shown by way ofillustration embodiments that may be practiced. It is to be understoodthat other embodiments may be utilized and structural or logical changesmay be made without departing from the scope of the present disclosure.

Various operations may be described as multiple discrete actions oroperations in turn, in a manner that is most helpful in understandingthe claimed subject matter. However, the order of description should notbe construed as to imply that these operations are necessarily orderdependent. In particular, these operations may not be performed in theorder of presentation. Operations described may be performed in adifferent order than the described embodiment. Various additionaloperations may be performed or described operations may be omitted inadditional embodiments.

For the purposes of the present disclosure, the term “or” is used as aninclusive term to mean at least one of the components coupled with theterm. For example, the phrase “A or B” means (A), (B), or (A and B); andthe phrase “A, B, or C” means (A), (B), (C), (A and B), (A and C), (Band C), or (A, B, and C).

The description may use the phrases “in an embodiment,” or “inembodiments,” which may each refer to one or more of the same ordifferent embodiments. Furthermore, the terms “comprising,” “including,”“having,” and the like, as used with respect to embodiments of thepresent disclosure, are synonymous.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), or memory (shared,dedicated, or group) that execute one or more software or firmwareprograms, a combinational logic circuit, or other suitable hardwarecomponents that provide the described functionality.

FIG. 1 schematically illustrates a wireless communication environment100 in accordance with various embodiments. The environment 100 mayinclude a user equipment (UE) 102 that is capable of communicating overone or more wireless communication networks. For example, the UE 102 maybe configured to communicate over a cellular network and a wirelesslocal area network (WLAN). The cellular network may utilize any suitableradio access technology (RAT), such as universal terrestrial radioaccess (UTRA) in accordance with a 3rd Generation Partnership Project(3GPP) universal mobile telecommunications system (UMTS) protocol orevolved UTRA (E-UTRA) in accordance with a 3GPP Long Term Evolution(LTE) protocol. The UE 102 may include carrier monitoring controlcircuitry 104 coupled with radio hardware 108 via a radio controlcircuitry 106. The carrier monitoring control circuitry 104 may controlcarrier monitoring-related operations of the UE 102. The radio controlcircuitry 106 may include circuitry for receiving signals from the radiohardware 108 for processing by the carrier monitoring control circuitry104 and/or circuitry for providing signals to the radio hardware 108from the carrier monitoring control circuitry 104. In some embodiments,the radio control circuitry 106 may be provided by computer-readableinstructions, stored in one or more computer-readable media, that may beexecuted by one or more processing devices included in the carriermonitoring control circuitry 104. The UE 102 may use the radio hardware108 to wirelessly communicate with one or more other devices in thewireless communication environment 100 (e.g., the eNB 112, discussedbelow). The radio hardware 108 may include any suitable conventionalhardware for performing wireless communications (e.g., an antenna 109),such as radio transmit circuitry and receive circuitry. In someembodiments, transmit and/or receive circuitry of the radio hardware 108may be elements or modules of transceiver circuitry. The UE 102 mayinclude other circuitry 110, which may perform any suitable functions (anumber of examples of which are discussed herein).

The wireless communication environment 100 may also include an eNB(which may also be referred to as an “evolved NodeB” or an “eNodeB”) 112that may be part of a cellular network as discussed above. The eNB 112may serve as the intermediary between one or more UEs (e.g., the UE 102)and a backbone network of the wireless communication environment 100.The geographic area over which the eNB 112 may provide such service maybe referred to as the cell associated with the eNB 112. When the UE 102is receiving such service from the eNB 112, the UE 102 may be referredto as being within the serving cell of the eNB 112. The eNB 112 mayinclude carrier monitoring control circuitry 114 coupled with radiohardware 118 via a radio control circuitry 116. The carrier monitoringcontrol circuitry 114 may control carrier monitoring-related operationof the eNB 112. The radio control circuitry 116 may include circuitryfor receiving signals from the radio hardware 118 for processing by thecarrier monitoring control circuitry 114 and/or circuitry for providingsignals to the radio hardware 118 from the carrier monitoring controlcircuitry 114. In some embodiments, the radio control circuitry 116 maybe provided by computer-readable instructions, stored in one or morecomputer-readable media, that may be executed by one or more processingdevices included in the carrier monitoring control circuitry 114. TheeNB 112 may use the radio hardware 118 to wirelessly communicate withone or more other devices in the wireless communication environment 100(e.g., the UE 102). The radio hardware 118 may include any suitableconventional hardware for performing wireless communications (e.g., anantenna 119), such as radio transmit circuitry and receive circuitry. Insome embodiments, transmit and/or receive circuitry of the radiohardware 118 may be elements or modules of transceiver circuitry. TheeNB 112 may include other circuitry 120, which may perform any suitablefunctions, such as wired or wireless communication with a networkcontroller (not shown).

The wireless environment 100 may also include a legacy eNB 122. Thelegacy eNB 122 may operate in accordance with a previous release of theUMTS protocol or a previous release of the LTE protocol (e.g., Release11). At various times, the UE 102 may be in communication with thelegacy eNB 122.

Although a single UE 102 and a single eNB 112 are depicted in FIG. 1,this is simply for ease of illustration, and the wireless environment100 may include one or more UEs configured as described herein withreference to the UE 102 and one or more eNBs configured as describedherein with reference to the eNB 112. For example, the UE 102 may beconfigured for communication with one or more eNBs configured asdescribed herein with reference to the eNB 112 (and for communicationwith one or more legacy eNBs configured as described herein withreference to the legacy eNB 122), and the eNB 112 may be configured forcommunication with more than one UE configured as described herein withreference to the UE 102.

The carrier monitoring control circuitry 104 may be configured to causethe UE 102 to detect, synchronize, and monitor intra-frequency,inter-frequency, and inter-RAT cells. These cells may be indicated inthe measurement control system information of the serving cell andprovided to the UE 102 by the eNB (e.g., the eNB 112). The UE 102 mayuse this information for, for example, cell re-selection.

The carrier monitoring control circuitry 104 of the UE 102 may beconfigured to support increased carrier monitoring by the UE 102. Asused herein “increased carrier monitoring” may refer to the monitoringof more carriers that was required in previous releases of the UMTS orLTE protocols. Table 1 below summarizes an example of the increasednumber of carriers of various types for a UE that supports increasedcarrier monitoring UTRA (using the UMTS protocol), and Table 2 belowsummarizes an example of the increased number of carriers of varioustypes for a UE that supports increased carrier monitoring E-UTRA (usingthe LTE protocol).

TABLE 1 Increased carrier monitoring requirements for a UE that supportsincreased carrier monitoring UTRA. Previous # of Increased # of UMTSCarriers Carriers UTRA FDD 2 4 LTE FDD/TDD 4 8

TABLE 2 Increased carrier monitoring requirements for a UE that supportsincreased carrier monitoring E-UTRA. Previous # of Increased # of LTECarriers Carriers UTRA FDD 3 6 UTRA TDD 3 7 LTE FDD/TDD 3 8

In some embodiments, a UE that is not performing increased carriermonitoring may, when in the Dedicated Channel (CELL_DCH) state and asingle uplink carrier frequency is configured, be required to be able tomonitor up to 32 intra-frequency division duplex (FDD) cells (includingin active set); 32 inter-frequency cells, including FDD cellsdistributed on up to 2 additional FDD carriers, and, depending on UEcapability, time division duplex (TDD) cells distributed on up to 3 TDDcarriers; depending on UE capability, 32 Global System for MobileCommunications (GSM) cells distributed on up to 32 GSM carriers;depending on UE capability, 4 E-UTRA FDD cells per E-UTRA FDD carrierfor up to 4 E-UTRA FDD carriers; depending on UE capability, 4 E-UTRATDD cells per E-UTRA TDD carrier for up to 4 E-UTRA TDD carriers; and,depending on UE capability, up to 16 intra frequency cells during IdlePeriod in the Downlink (IPDL) gaps. In addition to these requirements,in some embodiments, a UE supporting E-UTRA measurements, but that isnot performing increased carrier monitoring, shall be capable ofmonitoring a minimum total of at least 8 carrier frequency layers,including the intra-frequency serving layer and including anycombination of E-UTRA FDD, E-UTRA TDD, UTRA FDD, UTRA TDD, and GSMlayers as discussed above (one GSM layer corresponds to 32 cells).

In some embodiments, a UE that is not performing increased carriermonitoring may, when in the CELL_DCH state and dual uplink carrierfrequencies are configured, be required to be able to monitor up to 32intra frequency FDD cells (including in active set) per intra-frequencycarrier, 32 inter_frequency cells, including FDD cells distributed on upto 2 additional FDD carriers and, depending on UE capability, TDD cells,distributed on up to 3 TDD carriers; depending on UE capability, 32 GSMcells distributed on up to 32 GSM carriers; depending on UE capability,4 E-UTRA FDD cells per E-UTRA FDD carrier for up to 4 E-UTRA FDDcarriers; depending on UE capability, 4 E-UTRA TDD cells per E-UTRA TDDcarrier distributed on up to 4 E-UTRA TDD carriers; and, depending on UEcapability, up to 16 intra-frequency cells during IPDL gaps. In additionto these requirements, in some embodiments, a UE supporting E-UTRAmeasurements, but that is not performing increased carrier monitoring,shall be capable of monitoring a minimum total of at least 9 carrierfrequency layers, including the two intra-frequency carriers andincluding any combination of E-UTRA FDD, E-UTRA TDD, UTRA FDD, UTRA TDD,and GSM layers discussed above (one GSM layer corresponds to 32 cells).

In some embodiments, a UE that is not performing increased carriermonitoring may, when in the Cell Forward Access Channel (CELL_FACH)state, be required to be able to monitor up to 32 intra-frequency FDDcells and 32 inter-frequency cells, including FDD cells distributed onup to 2 additional FDD carriers; depending on UE capability, TDD modecells, distributed on up to 3 TDD carriers; depending on UE capability,32 GSM cells distributed on up to 32 GSM carriers; depending on UEcapability, up to 4 E-UTRA FDD carriers; depending on UE capability, upto 4 E-UTRA TDD carriers; and, depending on UE capability, up to 16intra-frequency cells during IPDL gaps.

By contrast, in some embodiments, a UE that indicates support forincreased carrier monitoring UTRA may additionally be capable ofmonitoring at least 80 inter-frequency cells, including 5 FDD UTRAinter-frequency carriers with up to 32 cells per carrier. In someembodiments, a UE that indicates support for increased UE carriermonitoring E-UTRA shall be capable of monitoring at least, depending onUE capability, 8 FDD E-UTRA carriers, and, depending on UE capability, 8TDD E-UTRA carriers. Additionally, in some embodiments, a UE supportingE-UTRA measurements and supporting increased carrier monitoring UTRA orincreased carrier monitoring E-UTRA may, when High Speed Downlink SharedChannel (HS-DSCH) discontinuous reception is ongoing, be capable ofmonitoring a total of at least 13 carrier frequency layers, whichincludes a serving layer, including any combination of E-UTRA FDD,E-UTRA TDD, UTRA FDD, UTRA TDD and GSM layers as discussed above (oneGSM layer corresponds to 32 cells).

When the UE 102 supports increased carrier monitoring (e.g., in UTRA orE-UTRA), and the eNB 112 recognizes such increased carrier monitoring,the set of inter-frequency carriers or inter-RAT carriers may be dividedinto two groups. The group that has a better delay performance comparedto the other group is referred to as the normal performance group (NPG)and the group that has worse delay performance compared to the othergroup is referred to as the reduced performance group (RPG). Table 3below summarizes an example of the maximum number of carriers of varioustypes that may be included in an NPG for a UE that supports increasedcarrier monitoring UTRA (using the UMTS protocol), and Table 4 belowsummarizes an example of the maximum number of carriers of various typesthat may be included in an NPG for a UE that supports increased carriermonitoring E-UTRA (using the LTE protocol). The values in Tables 3 and 4may apply when the UE 102 is in connected mode (e.g., in the RadioResource Control Connected state (RRC_CONNECTED), in the Cell DedicatedChannel state (CELL_DCH), or in the Cell Forward Access Channel state(CELL_FACH)).

TABLE 3 Increased carrier monitoring requirements for a UE that supportsincreased carrier monitoring UTRA. # Carriers in UMTS NPG UTRA FDD ≤2LTE FDD/TDD ≤4

TABLE 4 Increased carrier monitoring requirements for a UE that supportsincreased carrier monitoring E-UTRA. # Carriers in LTE NPG UTRA FDD ≤3UTRA TDD ≤3 LTE FDD/TDD ≤3

The carrier monitoring control circuitry 104 may apply differentperformance requirements for various operations to NPG cells and to RPGcells. For example, when the UE 102 is configured for increased carriermonitoring, the carrier monitoring control circuitry 104 may beconfigured to identify a new detectable cell belonging to a monitoredset (the “performance delay requirement”) within

$\begin{matrix}{T_{{identify},{inter}} = {{T_{{{basic}\mspace{14mu}{identify}\mspace{14mu}{FDD}},{inter}} \cdot \frac{T_{{{Measurement}\mspace{14mu}{Period}},{Inter}}}{T_{Inter}} \cdot K_{N} \cdot N_{{Freq},n}}{ms}}} & (1)\end{matrix}$

for a carrier within an NPG, and may be configured to identify a newdetectable cell belonging to a monitored set within

$\begin{matrix}{T_{{identify},{inter}} = {{T_{{{basic}\mspace{14mu}{identify}\mspace{14mu}{FDD}},{inter}} \cdot \frac{T_{{{Measurement}\mspace{14mu}{Period}},{Inter}}}{T_{Inter}} \cdot K_{r} \cdot N_{{Freq},n}}{ms}}} & (2)\end{matrix}$

for a carrier within an RPG, wherein T_(basic identify FDD,inter) may be300 ms (or another suitable value); T_(Measuremer Period,Inter) may be480 ms (or another suitable value); T_(Inter) may be the minimum timeavailable for inter-frequency measurements; N_(Freq,n) may be the numberof carriers to be searched for and measured with normal performance;N_(Freq,r) may be the number of carriers to be searched for and measuredwith reduced performance; K_(n) may be equal to 1 if N_(Freq,r) is zero(i.e., all carriers to be searched for and measured are in the NPG) andmay be equal S/(S−1) if N_(Freq,r) is non-zero, where S is a scalingfactor; and K_(r) may be equal to S if N_(Freq,r) is not equal to zero.The scaling fact or S may define the relaxation to be applied to therequirements for carriers measured with reduced measurement performance,and may be signalled by higher layers.

These are simply examples, and the carrier monitoring control circuitry104 may treat NPG carriers and RPG carriers differently in a number ofways (including those discussed elsewhere herein).The legacy eNB 122 maynot be configured to recognize increased carrier monitoring by the UE102 (e.g., because the legacy UMTS or LTE protocol did not include orrecognize increased carrier monitoring). For example, instead ofexpecting the UE 102 to perform measurements for identifying a newdetectable cell in accordance with Eqs. 1 and 2 above, the legacy eNB122 may expect the UE 102 to perform measurements for identifying a newdetectable cell in accordance with

$\begin{matrix}{T_{{identify},{inter}} = {{T_{{{basic}\mspace{14mu}{identify}\mspace{14mu}{FDD}},{inter}} \cdot \frac{T_{{{Measurement}\mspace{14mu}{Period}},{Inter}}}{T_{Inter}} \cdot N_{{Freq},{legacy}}}{ms}}} & (3)\end{matrix}$

where N_(Freq) may be the number of carriers to be searched for andmeasured in accordance with the legacy protocol.

However, in conventional systems, a UE may not know whether a servingeNB supports increased carrier monitoring or does not support increasedcarrier monitoring when all carriers are NPG (and thus no carriers areindicated as RPG). This may lead to performance failures, as theconventional UE that supports increased carrier monitoring will notknow, for example, that the UE is required to monitor 8 FDD carrierswhen the serving eNB supports increased carrier monitoring and is onlyrequired to monitor 3 FDD carrier when the serving eNB does not supportincreased carrier monitoring. In another example, performance failuresmay occur if the UE does not know the period within which a newdetectable cell belonging to a monitored set may be identified (e.g.,whether Eqs. (1) and (2) should be applied, or Eq. (3) should beapplied).

In a first set of embodiments, these issues may be addressed byrequiring the carrier monitoring control circuitry 114 of the eNB 112 toconfigure at least one RPG carrier when the UE 102 is first served bythe cell associated with the eNB 112. By signaling to the UE 102 thatthere is at least one RPG carrier, the eNB 112 may indicate to the UE102 that the eNB 112 supports increased carrier monitoring, and thusthat, for example, Eqs. 1 and 2 should be used. If the eNB 112 does notintend for any carriers to be treated as RPG, the carrier monitoringcontrol circuitry 114 may subsequently change the configuration tosignal to the UE 102 that all carriers are NPG (after the UE 102 hasreceived the previous RPG indication and thus concluded that the eNB 112supports increased carrier monitoring).

In a second set of embodiments, the issues identified above may beaddressed by requiring the carrier monitoring control circuitry 114 ofthe eNB 112 to configure at least one RPG carrier when the UE 102 isfirst served by the cell associated with the eNB 112, and also toconfigure the scaling factor to define the relaxation to be applied tothe requirements for RPG carriers. By signaling the scaling factor tothe UE 102, the eNB 112 may indicate to the UE 102 that the eNB 112supports increased carrier monitoring, and thus that, for example, Eqs.1 and 2 should be used. If, as discussed above with reference to thefirst set of embodiments, the eNB 112 does not intend for any carriersto be treated as RPG, the carrier monitoring control circuitry 114 maysubsequently change the configuration to signal to the UE 102 that allcarriers are NPG (after the UE 102 has received the scaling factorindication and thus concluded that the eNB 112 supports increasedcarrier monitoring).

In a third set of embodiments, the issues identified above may beaddressed by configuring the UE 102 and the eNB 112 to utilize thescaling factor as an indicator of whether increased carrier monitoringshould or should not be performed when all carriers are NPG, withouthaving to initially configure a carrier as RPG. When the UE 102 detectsthe presence of the scaling factor in a communication from the eNB 112when all carriers are NPG, the carrier monitoring control circuitry 104may interpret this condition as indicating that the eNB 112 supportsincreased carrier monitoring, and may apply Eq. 1 (which, when there areno RPG carriers configured, does not depend on the scaling factor). Inthe second and third sets of embodiments, since the scaling factorcommunicates information about the relaxation to be applied tomeasurement requirements for RPG carriers, using the scaling factor tocommunicate additional information may be a form of implicit signaling,and may have the advantage of not requiring much or any additional datato be communicated between an eNB and a UE.

Table 5 below illustrates a portion of an example system informationblock that may be used by the carrier monitoring control circuitry 114of the eNB 112 to signal carrier information to the UE 102, inaccordance with some embodiments. As shown in Table 5, an informationelement reducedMeasurementPerformance-r12 is indicated as “OPTIONAL NeedOR,” which means that the information element is optional for the eNB112 to signal, but if the message is received by the UE 102 and theinformation element is absent, the UE 102 shall discontinue/stopusing/delete any existing value (and/or the associated functionality).In the example of Table 5, the information elementsInterFreqCarrierFreqInfo-v12xy and InterFreqCarrierFreqInfo-r12 may actas different ways for the eNB 112 to indicate the RPG carriers and maybe included for compatibility reasons.

TABLE 5 System Information Block Type 6 information element.InterFreqCarrierFreqInfo-v12xy ::= SEQUENCE {reducedMeasurementPerformance-r12 ENUMERATED {true} OPTIONAL -- Need OR} ... InterFreqCarrierFreqInfo-r12 ::= SEQUENCE { dl-CarrierFreq-r12ARFCN-ValueEUTRA-r9, q-RxLevMin-r12 Q-RxLevMin, p-Max-r12 P-MaxOPTIONAL, -- Need OP t-ReselectionEUTRA-r12 T-Reselection,t-ReselectionEUTRA-SF-r12 SpeedStateScaleFactors OPTIONAL, -- Need OPthreshX-High-r12 ReselectionThreshold, threshX-Low- If the measId-v12xyis included12 ReselectionThreshold, allowedMeasBandwidth-r12AllowedMeasBandwidth, presenceAntennaPort1-r12 PresenceAntennaPort1,cellReselectionPriority-r12 CellReselectionPriority OPTIONAL, -- Need OPneighCellConfig-r12 NeighCellConfig, q-OffsetFreq-r12 Q-OffsetRangeDEFAULT dB0, interFreqNeighCellList-r12 InterFreqNeighCellList OPTIONAL,-- Need OR interFreqBlackCellList-r12 InterFreqBlackCellList OPTIONAL,-- Need OR q-QualMin-r12 Q-QualMin-r9 OPTIONAL, -- Need OP threshX-Q-r12SEQUENCE { threshX-HighQ-r12 ReselectionThresholdQ-r9, threshX-LowQ-r12ReselectionThresholdQ-r9 } OPTIONAL, -- Cond RSRQ q-QualMinWB-r12Q-QualMin-r9 OPTIONAL, - - Cond WB-RSRQ multiBandInfoList-r12MultiBandInfoList-r11 OPTIONAL, -- Need ORreducedMeasurementPerformance-r12 ENUMERATED {true} OPTIONAL, -- Need OR... }

Table 6 below illustrates an example information element that may beused by the carrier monitoring control circuitry 114 of the eNB 112 tosignal measurements to be performed by the UE 102, includingintra-frequency, inter-frequency, and inter-RAT mobility measurements,as well as configuration of measurement gaps. As shown in Table 6, aninformation element measScaleFactor-r12 is indicated as “OPTIONAL NeedON,” which means that the information element that is optional for theeNB 112 to signal, but if the message is received by the UE 102 and theinformation element is absent, the UE 102 takes no action and, whereapplicable, shall continue to use the existing value (and/or theassociated functionality). In some embodiments, the information elementmeasScaleFactor-r12 may be indicated as “OPTIONAL Need OR” instead of“OPTIONAL Need ON.” In some embodiments, the information elementmeasScaleFactor-r12 may be indicated as NON-OPTIONAL instead ofOPTIONAL. In Table 6, the information elements measldToRemoveListExt-r12and measldToAddModListExt-r12 may be used by the network to add orremove measurement objects from the list (e.g., to signal the change tothe UE 102).

TABLE 6 MeasConfig information element. -- ASN1START MeasConfig ::=SEQUENCE { -- Measurement objects measObjectToRemoveListMeasObjectToRemoveList OPTIONAL, -- Need ON measObjectToAddModListMeasObjectToAddModList OPTIONAL, -- Need ON -- Reporting configurationsreportConfigToRemoveList ReportConfigToRemoveList OPTIONAL, -- Need ONreportConfigToAddModList ReportConfigToAddModList OPTIONAL, -- Need ON-- Measurement identities measIdToRemoveList MeasIdToRemoveListOPTIONAL, -- Need ON measIdToAddModList MeasIdToAddModList OPTIONAL, --Need ON -- Other parameters quantityConfig QuantityConfig OPTIONAL, --Need ON measGapConfig MeasGapConfig OPTIONAL, -- Need ON s-MeasureRSRP-Range OPTIONAL, -- Need ON preRegistrationInfoHRPDPreRegistrationInfoHRPD OPTIONAL, -- Need OP speedStatePars CHOICE {release NULL, setup SEQUENCE { mobilityStateParametersMobilityStateParameters, timeToTrigger-SF SpeedStateScaleFactors } }OPTIONAL, -- Need ON ..., [[ measObjectToAddModList-v9e0MeasObjectToAddModList-v9e0 OPTIONAL -- Need ON ]], [[measScaleFactor-r12 MeasScaleFactor-r12 OPTIONAL, -- Need ONmeasIdToRemoveListExt-r12 MeasIdToRemoveListExt-r12 OPTIONAL, -- Need ONmeasIdToAddModListExt-r12 MeasIdToAddModListExt-r12 OPTIONAL  -- Need ON]] } MeasIdToRemoveList ::= SEQUENCE (SIZE (1..maxMeasId)) OF MeasIdMeasIdToRemoveListExt-r12 ::= SEQUENCE (SIZE (1..maxMeasId)) OFMeasId-v12xy MeasObjectToRemoveList ::= SEQUENCE (SIZE (1..maxObjectId))OF MeasObjectId ReportConfigToRemoveList ::= SEQUENCE (SIZE(1..maxReportConfigId)) OF ReportConfigId -- ASN1STOP

Table 7 below illustrates an example MeasScaleFactor-r12 informationelement that may be used by the carrier monitoring control circuitry 114of the eNB 112 to signal the scaling factor to be used for scaling themeasurement performance requirements when the UE 102 is configured withUTRA and E-UTRA frequencies for reduced measurement performance. Inparticular, the sf-Measurement field of the MeasScaleFactor-r12information element may specify the factor used to scale the measurementperformance for UTRA and E-UTRA frequencies, when applicable. In someembodiments, the information element MeasScaleFactor-r12 may beindicated as “OPTIONAL Need OR” instead of “OPTIONAL Need ON.” In someembodiments, the information element MeasScaleFactor-r12 may beindicated as NON-OPTIONAL instead of OPTIONAL.

TABLE 7 MeasScaleFactor information element. -- ASN1STARTMeasScaleFactor-r12 ::= SEQUENCE { sf-Measurement ENUMERATED {sf8, sf16}OPTIONAL - - Need OR } -- ASN1STOP

In some embodiments, the carrier monitoring control circuitry 114 of theeNB 112 may signal a designated “NONE” or other value for the scalingfactor (e.g., in the sf-Measurement field of the MeasScaleFactor-r12information element discussed above) to specify that all carriers are tobe considered NPG, instead of providing an otherwise valid scalingfactor value.

In some embodiments, the carrier monitoring control circuitry 114 of theeNB 112 may configure a scaling factor (e.g., in accordance with theMeasScaleFactor-r12 information element of Table 6) at a different timethan the signaling of the carriers (e.g., in accordance with the SystemInformation Block of Table 5). In other embodiments, the carriermonitoring control circuitry 114 of the eNB 112 may be required toconfigure the scaling factor and signal the carriers at the same time(e.g., by including scaling factor information in theInterFreqCarrierFreqInfo-r12 information element discussed above withreference to Table 5).

FIG. 2 is a flow diagram of a process 200 for operating a UE. For easeof illustration, the process 200 may be discussed below with referenceto the UE 102. It may be recognized that, while the operations of theprocess 200 (and the other processes described herein) are arranged in aparticular order and illustrated once each, in various embodiments, oneor more of the operations may be repeated, omitted, or performed out oforder. For example, operations related to determining whether an RPGcarrier is configured may be performed before, after, or in parallelwith operations related to determining whether a scaling factor isconfigured. For illustrative purposes, operations of the process 200 maybe described as performed by the carrier monitoring control circuitry104 of the UE 102, but the process 200 may be performed by any suitablyconfigured device (e.g., a programmed processing system, an ASIC, oranother wireless computing device).

At 202, the carrier monitoring control circuitry 104 may determinewhether an RPG carrier is configured (e.g., based on a signal providedby the eNB 112 or the legacy eNB 122). For example, if the UE 102receives a System Information Block configured as described above withreference to the System Information Block of Table 5, the carriermonitoring control circuitry 104 may process the information containedtherein to determine whether an RPG carrier is configured. In anotherexample, if the UE 102 does not receive any signal from an eNBindicating that an RPG is configured, the carrier monitoring controlcircuitry 104 may determine that no RPG is configured.

If the carrier monitoring control circuitry 104 determines at 202 thatno RPG carrier is configured, the carrier monitoring control circuitry104 may determine that all carriers will be considered to have normalperformance (e.g., be included in the NPG) at 204. The carriermonitoring control circuitry 104 may then determine whether a scalingfactor is configured at 206. For example, if the UE 102 receives aMeasScaleFactor information element as described above with reference tothe MeasScaleFactor information element of Table 7, the carriermonitoring control circuitry 104 may process the information containedtherein to determine whether a scaling factor is configured. In anotherexample, if the UE 102 does not receive any signal from an eNBindicating that a scaling factor is configured, the carrier monitoringcontrol circuitry 104 may determine that no scaling factor isconfigured.

If the carrier monitoring control circuitry 104 determines at 206 thatno scaling factor is configured, the carrier monitoring controlcircuitry 104 may determine at 208 that the UE 102 is not required tomonitor an increased number of carriers and may instead monitor a“legacy” number of carriers. In some embodiments, this may occur whenthe eNB serving the UE 102 is the legacy eNB 122 and does not supportincreased carrier monitoring. Thus, if no RPG carrier is configured andno scaling factor is configured, a UE 102 that indicates support forincreased carrier monitoring (E-UTRA or UTRA) may not be required tomonitor the increased number of carriers specified by increased carriermonitoring.

If the carrier monitoring control circuitry 104 determines at 206 that ascaling factor is configured, the carrier monitoring control circuitry104 may determine at 210 that the UE 102, which supports increasedcarrier monitoring, is to perform increased carrier monitoring.

Returning to 202, if the carrier monitoring control circuitry 104determines at 202 that an RPG carrier is configured, the carriermonitoring control circuitry 104 may proceed to 212 and determinewhether a scaling factor is configured.

If the carrier monitoring control circuitry 104 determines at 212 thatno scaling factor is configured, the carrier monitoring controlcircuitry 104 may determine at 216 to perform any of a number ofoperations. In some embodiments, the carrier monitoring controlcircuitry 104 may, at 216, apply a set of default reduced measurementperformance requirements to carriers in the RPG. These default reducedmeasurement performance requirements may be specified in a wirelesscommunication specification (e.g., a 3GPP specification). For example,the carrier monitoring control circuitry 104 may use a previouslysignaled scaling factor. In some embodiments, the carrier monitoringcontrol circuitry 104 may, at 216, determine that a networkmisconfiguration has occurred, and may signal to another component(e.g., an eNB) that a misconfiguration has taken place. In someembodiments, the carrier monitoring control circuitry 104 may, at 216,consider all carriers to be NPG due to the lack of a scaling factor(despite the determination at 202 that at least one RPG carrier isconfigured), and may not follow increased carrier monitoring performancerequirements.

If the carrier monitoring control circuitry 104 determines at 212 that ascaling factor is configured, the carrier monitoring control circuitry104 may determine at 218 that the scaling factor is to be applied todefine the relaxation to be applied to requirements for RPG carriers(e.g., in accordance with Eq. 3 above).

FIG. 3 is a flow diagram of a process 300 for operating a UE. For easeof illustration, the process 300 may be discussed below with referenceto the UE 102. For illustrative purposes, operations of the process 300may be described as performed by the carrier monitoring controlcircuitry 104 of the UE 102, but the process 300 may be performed by anysuitably configured device (e.g., a programmed processing system, anASIC, or another wireless computing device).

At 302, the carrier monitoring control circuitry 104 may configure theUE 102 to support increased carrier monitoring. In some embodiments,increased carrier monitoring may require the UE 102 to monitor thenumber and type of carriers discussed above. For example, increasedcarrier monitoring may require the UE 102 to monitor more than fourE-UTRA or UTRA FDD carriers, and/or more than four E-UTRA or UTRA TDDcarriers.

At 304, the carrier monitoring control circuitry 104 may receive, viathe radio control circuitry 106, one or more signals from an eNB. Theone or more signals may indicate whether an RPG carrier is configuredand whether a scaling factor is configured. For example, when the eNB isthe legacy eNB 122, signals from the eNB 122 may not indicate that anRPG carrier is configured and may not indicate that a scaling factor isconfigured. When the eNB is the eNB 112, signals from the eNB 112 mayindicate whether an RPG carrier is configured, and may indicate a valuefor the scaling factor.

At 306, the carrier monitoring control circuitry 104 may determine,based on the one or more signals from the eNB, whether an RPG carrier isconfigured. For example, if the UE 102 receives a System InformationBlock configured as described above with reference to the SystemInformation Block of Table 5, the carrier monitoring control circuitry104 may process the information contained therein to determine whetheran RPG carrier is configured. In another example, if the UE 102 does notreceive any signal from an eNB indicating that an RPG is configured, thecarrier monitoring control circuitry 104 may determine that no RPG isconfigured.

At 308, the carrier monitoring control circuitry 104 may determine,based on the one or more signals from the eNB, whether a scaling factoris configured. For example, if the UE 102 receives a MeasScaleFactorinformation element as described above with reference to theMeasScaleFactor information element of Table 7, the carrier monitoringcontrol circuitry 104 may process the information contained therein todetermine whether a scaling factor is configured. In another example, ifthe UE 102 does not receive any signal from an eNB indicating that ascaling factor is configured, the carrier monitoring control circuitry104 may determine that no scaling factor is configured.

At 310, the carrier monitoring control circuitry 104 may, in response toa determination that no RPG carrier is configured and a determinationthat no scaling factor is configured, allow the UE 102 to monitor anon-increased number of carriers. For example, the UE 102 may be allowedto monitor four or fewer E-UTRA or UTRA FDD carriers and/or four orfewer E-UTRA or UTRA TDD carriers.

FIG. 4 is a flow diagram of a process 400 for operating an eNB. For easeof illustration, the process 400 may be discussed below with referenceto the eNB 112 in communication with the UE 102. For illustrativepurposes, operations of the process 400 may be described as performed bythe carrier monitoring control circuitry 114 of the eNB 112, but theprocess 400 may be performed by any suitably configured device (e.g., aprogrammed processing system, an ASIC, or another wireless computingdevice).

At 402, the carrier monitoring control circuitry 114 may causetransmission, via the radio control circuitry 116, of a first signal tothe UE 102. The UE 102 may support increased carrier monitoringperformance, and the first signal may indicate that no RPG carrier isconfigured. For example, the carrier monitoring control circuitry 114may cause the transmission of a System Information Block configured asdescribed above with reference to the System Information Block of Table5, wherein the information in the System Information Block indicatesthat no RPG is configured.

At 404, the carrier monitoring control circuitry 114 may causetransmission, via the radio control circuitry 116, of a second signal tothe UE 102. The second signal may indicate that a scaling factor isconfigured. For example, the carrier monitoring control circuitry 114may cause the transmission of a MeasScaleFactor information element asdescribed above with reference to the MeasScaleFactor informationelement of Table 7, wherein the information in the MeasScaleFactorinformation element indicates the value of the scaling factor.

At 406, the carrier monitoring control circuitry 114 may receive, fromthe UE 102 via the radio control circuitry 116, measurements made by theUE in accordance with increased carrier monitoring.

For example, the UE 102 may be required to monitor more than four E-UTRAor UTRA FDD carriers and/or more than four E-UTRA or UTRA TDD carriers.

In the process 400, if the UE 102 did not support increased carriermonitoring, receipt of the indication of no RPG carriers and receipt ofthe indication of a scaling factor may not cause the UE 102 to makemeasurements in accordance with increased carrier monitoringperformance. Instead, since increased carrier monitoring is notsupported, the UE 102 may simply make measurements in accordance withnon-increased carrier monitoring.

The UE 102 or eNB 112 as described herein may be implemented into asystem using any suitable hardware, firmware, or software configured asdesired. FIG. 5 illustrates, for one embodiment, an example system 500comprising radio frequency (RF) circuitry 504, baseband circuitry 508,application circuitry 512, memory/storage 516, display 520, camera 524,sensor 528, input/output (I/O) interface 532, or network interface 536coupled with each other as shown. In some embodiments, the RF circuitry504 and the baseband circuitry 508 may be included in the radio hardware108 or the radio hardware 118 for the UE 102 or the eNB 112,respectively. In some embodiments, the application circuitry 512 may beincluded in the carrier monitoring control circuitry 104 or the carriermonitoring control circuitry 114 for the UE 102 or the eNB 112,respectively. Other circuitry of the system 500 may be included in theother circuitry 110 or the other circuitry 120 of the UE 102 or the eNB112, respectively.

The application circuitry 512 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Theprocessor(s) may include any combination of general-purpose processorsand dedicated processors (e.g., graphics processors, applicationprocessors, etc.). The processors may be coupled with memory/storage 516and configured to execute instructions stored in the memory/storage 516to enable various applications or operating systems running on thesystem 500.

The baseband circuitry 508 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors such as,for example, a baseband processor. The baseband circuitry 508 may handlevarious radio control functions that enable communication with one ormore radio access networks via the RF circuitry 504. The radio controlfunctions may include, but are not limited to, signal modulation,encoding, decoding, radio frequency shifting, etc. In some embodiments,the baseband circuitry 508 may provide for communication compatible withone or more radio technologies. For example, in some embodiments, thebaseband circuitry 508 may support communication with an E-UTRAN orother wireless metropolitan area networks (WMAN), a wireless local areanetwork (WLAN), or a wireless personal area network (WPAN). Embodimentsin which the baseband circuitry 508 is configured to support radiocommunications of more than one wireless protocol may be referred to asmulti-mode baseband circuitry.

In various embodiments, baseband circuitry 508 may include circuitry tooperate with signals that are not strictly considered as being in abaseband frequency. For example, in some embodiments, baseband circuitry508 may include circuitry to operate with signals having an intermediatefrequency, which is between a baseband frequency and a radio frequency.

The RF circuitry 504 may enable communication with wireless networksusing modulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 504 may include switches, filters,amplifiers, etc., to facilitate the communication with the wirelessnetwork.

In various embodiments, RF circuitry 504 may include circuitry tooperate with signals that are not strictly considered as being in aradio frequency. For example, in some embodiments, RF circuitry 504 mayinclude circuitry to operate with signals having an intermediatefrequency between a baseband frequency and a radio frequency.

In some embodiments, some or all of the constituent components of thebaseband circuitry 508, the application circuitry 512, or thememory/storage 516 may be implemented together on a system on a chip(SOC).

The memory/storage 516 may be used to load and store data orinstructions, for example, for the system 500. For example, thememory/storage 516 may provide one or more computer-readable media(e.g., non-transitory computer-readable media) having instructionsthereon that, in response to execution by one or more processing devicesof the system 500, cause the system 500 to perform any suitable process(e.g., any of the processes disclosed herein). The memory/storage 516for one embodiment may include any combination of suitable volatilememory (e.g., dynamic random access memory (DRAM)) or non-volatilememory (e.g., Flash memory).

In various embodiments, the I/O interface 532 may include one or moreuser interfaces designed to enable user interaction with the system 500or peripheral component interfaces designed to enable peripheralcomponent interaction with the system 500. User interfaces may include,but are not limited to, a physical keyboard or keypad, a touchpad, aspeaker, a microphone, etc. Peripheral component interfaces may include,but are not limited to, a non-volatile memory port, a universal serialbus (USB) port, an audio jack, and a power supply interface.

In various embodiments, the sensor 528 may include one or more sensingdevices to determine environmental conditions or location informationrelated to the system 500. In some embodiments, the sensors may include,but are not limited to, a gyro sensor, an accelerometer, a proximitysensor, an ambient light sensor, and a positioning unit. The positioningunit may also be part of, or interact with, the baseband circuitry 508or RF circuitry 504 to communicate with components of a positioningnetwork, e.g., a global positioning system (GPS) satellite.

In various embodiments, the display 520 may include a display (e.g., aliquid crystal display, a touch screen display, etc.). In variousembodiments, the network interface 536 may include circuitry tocommunicate over one or more wired networks.

In various embodiments, the system 500 may be a mobile computing devicesuch as, but not limited to, a laptop computing device, a tabletcomputing device, a netbook, an ultrabook, a smartphone, etc. In variousembodiments, the system 500 may have more or fewer components, ordifferent architectures.

The following paragraphs illustrate examples of various embodimentsdisclosed herein.

Example 1 may include configuration, by one or more network devices(such as an eNB) of at least one reduced performance group carrier, inresponse to which a UE may use the presence of a scaling factor or thepresence of the reduced performance group carrier to determine if thenetwork supports increased carrier monitoring or not, and may apply thecorresponding performance delay requirement accordingly.

Example 2 may include the subject matter of Example 1, and may furtherinclude configuration, by the one or more network devices, of thescaling factor when all carriers are configured as NPG, in response towhich the UE may still follow all NPG requirements and may not apply thescaling factor.

Example 3 may include the subject matter of Example 1, and may furtherinclude the UE following the performance requirements of all carriersconfigured as NPG with the scaling factor present (i.e., the UE shouldnot apply the scaling factor to measurements).

Example 4 may include the subject matter of any of Examples 1-3, and mayfurther include using a “none” value in the scaling factor to indicatethat all carriers are NPG.

Example 5 may include the subject matter of any of Examples 1-4, and mayfurther include the network being required to configure the scalingfactor and an inter-freq list at the same time (i.e., usingInterFreqCarrierFreqInfo-r12).

Example 6 may include the subject matter of any of Examples 1-5, and mayfurther specify that “measScaleFactor-r12 MeasScaleFactor-r12” should be“OPTIONAL, —Need OR” instead of “OPTIONAL,—Need ON.”

Example 7 may include the subject matter of any of Examples 1-6, and mayfurther specify that “measScaleFactor-r12 MeasScaleFactor-r12” should benon-optional.

Example 8 is a method for network device operation, includingconfiguring, by the network device of a wireless network, at least onereduced performance group carrier; and signaling, to a UE, a scalingfactor; wherein, in response, a UE may use the presence of the scalingfactor or the presence of the reduced performance group carrier todetermine if the wireless network supports increased carrier monitoringor not.

Example 9 may include the subject matter of Example 8, and may furtherspecify that the UE, in response, may apply a corresponding performancedelay requirement accordingly.

Example 10 may include the subject matter of any of Examples 8-9, andmay further include configuring, by the network device, the scalingfactor when all carriers are configured as NPG, in response to which theUE may still follow all NPG requirements and may not apply the scalingfactor.

Example 11 may include the subject matter of any of Examples 8-10, andmay further specify that configuring the scaling factor includes using a“none” value for the scaling factor to indicate that all carriers areNPG.

Example 12 may include the subject matter of any of Examples 8-11, andmay further configuring, by the network device, the scaling factor andan inter-frequency list at the same time.

Example 13 may include the subject matter of Example 12, and may furtherspecify that the scaling factor and the inter-frequency list areconfigured using InterFreqCarrierFreqInfo-r12.

Example 14 may include the subject matter of any of Examples 8-13, andmay further specify that “measScaleFactor-r12 MeasScaleFactor-r12” is“OPTIONAL,—Need OR.”

Example 15 may include the subject matter of any of Examples 8-14, andmay further specify that “measScaleFactor-r12 MeasScaleFactor-r12” isnon-optional.

Example 16 is a user equipment (UE) including: radio control circuitryto couple with radio hardware for wireless communications with an eNB;and carrier monitoring control circuitry, coupled with the radio controlcircuitry, to: configure the UE to support increased carrier monitoring,wherein increased carrier monitoring requires the UE to monitor morethan four radio access technology (RAT) frequency division duplex (FDD)carriers, and wherein the RAT is Evolved Universal Terrestrial RadioAccess (E-UTRA) or Universal Terrestrial Radio Access (UTRA); determine,based on one or more signals received from the eNB, whether a reducedperformance group carrier is configured; determine, based on the one ormore signals received from the eNB, whether a scaling factor isconfigured; and in response to a determination that no reducedperformance group carrier is configured and a determination that noscaling factor is configured, allow the UE to monitor four or fewer RATFDD carriers.

Example 17 may include the subject matter of Example 16, and may furtherspecify that: increased carrier monitoring further requires the UE tomonitor more than four RAT time division duplex (TDD) carriers; and thecarrier monitoring control circuitry is to, in response to adetermination that no reduced performance group carrier is configuredand a determination that no scaling factor is configured, allow the UEto monitor four or fewer RAT TDD carriers.

Example 18 may include the subject matter of any of Examples 16-17, andmay further specify that the carrier monitoring control circuitry is to,in response to a determination that no reduced performance group carrieris configured and a determination that a scaling factor is configured,require the UE to monitor more than four RAT FDD carriers.

Example 19 may include the subject matter of any of Examples 16-18, andmay further specify that the scaling factor defines a relaxation to beapplied to measurements for reduced performance group carriers.

Example 20 may include the subject matter of Example 19, and may furtherspecify that the carrier monitoring control circuitry is to, in responseto a determination that one or more reduced performance group carriersare configured and a determination that a scaling factor is configured,require the UE to monitor the one or more reduced performance groupcarrier based at least in part on the scaling factor.

Example 21 may include the subject matter of any of Examples 16-20, andmay further specify that increased carrier monitoring requires the UE tomonitor at least eight RAT FDD carriers.

Example 22 may include the subject matter of any of Examples 16-21, andmay further specify that the carrier monitoring control circuitry is todetermine whether a reduced performance group carrier is configuredbased on a reduced measurement performance field of an informationelement.

Example 23 may include the subject matter of any of Examples 16-22, andmay further specify that the carrier monitoring control circuitry is todetermine whether a scaling factor is configured based on aMeasScaleFactor information element.

Example 24 may include the subject matter of any of Examples 16-23, andmay further include a global positioning system receiver.

Example 25 is one or more non-transitory computer-readable media havinginstructions thereon that, in response to execution by one or moreprocessing devices of a user equipment (UE), cause the UE to: determine,based on one or more signals received by the UE from an eNB, whether areduced performance group carrier is configured, wherein the UE supportsincreased carrier monitoring, increased carrier monitoring requires theUE to monitor more than four radio access technology (RAT) frequencydivision duplex (FDD) carriers, and wherein the RAT is Evolved UniversalTerrestrial Radio Access (E-UTRA) or Universal Terrestrial Radio Access(UTRA); determine, based on the one or more signals received from theeNB, whether a scaling factor is configured; and in response to adetermination that no reduced performance group carrier is configuredand a determination that no scaling factor is configured, allow the UEto monitor four or fewer RAT FDD carriers.

Example 26 may include the subject matter of Example 25, and may furtherspecify that the one or more signals includes a MeasScaleFactorinformation element that indicates that the scaling factor isconfigured.

Example 27 may include the subject matter of any of Examples 25-26, andmay further specify that the scaling factor defines a relaxation to beapplied to measurements for reduced performance group carriers.

Example 28 may include the subject matter of Example 27, and may furtherspecify that the instructions are further to, in response to executionby the one or more processing devices of the UE, cause the UE to:receive an additional signal, from the eNB, that indicates that one ormore reduced performance group carriers are configured; and provide, tothe eNB in response to the additional signal, measurements of the one ormore reduced performance group carriers made in accordance with thescaling factor.

Example 29 is an eNB, including: radio control circuitry to couple withradio hardware for wireless communications; and carrier monitoringcontrol circuitry, coupled with the radio control circuitry, to: causetransmission of a first signal to a user equipment (UE), wherein thefirst signal indicates that no reduced performance group carrier isconfigured, the UE is configured to support increased carriermonitoring, increased carrier monitoring requires the UE to monitor morethan four radio access technology (RAT) frequency division duplex (FDD)carriers, and the RAT is Evolved Universal Terrestrial Radio Access(E-UTRA) or Universal Terrestrial Radio Access (UTRA); causetransmission of a second signal to the UE, wherein the second signalindicates that a scaling factor is configured; and receive, from the UE,increased carrier monitoring measurements, wherein the increased carriermonitoring measurements include measurements of more than four RAT FDDcarriers, wherein the UE performs the increased carrier monitoringmeasurements in response to receipt of the first and second signals.

Example 30 may include the subject matter of Example 29, and may furtherspecify that the second signal includes a MeasScaleFactor informationelement that indicates that a scaling factor is configured.

Example 31 may include the subject matter of any of Examples 29-30, andmay further specify that the scaling factor defines a relaxation to beapplied to measurements for reduced performance group carriers.

Example 32 may include the subject matter of Example 31, and may furtherspecify that the carrier monitoring control circuitry is to: causetransmission of a third signal to the UE, wherein the third signalindicates that one or more reduced performance group carriers areconfigured; and receive, from the UE, in response to the third signal,measurements of the one or more reduced performance group carriers madein accordance with the scaling factor.

Example 33 may include the subject matter of any of Examples 29-32, andmay further include radio hardware including an antenna.

Example 34 is one or more non-transitory computer-readable media havinginstructions thereon that, in response to execution by one or moreprocessing devices of an eNB, cause the eNB to: cause transmission of afirst signal to a user equipment (UE), wherein the first signalindicates that no reduced performance group carrier is configured, theUE is configured to support increased carrier monitoring, increasedcarrier monitoring requires the UE to monitor more than four radioaccess technology (RAT) frequency division duplex (FDD) carriers, andthe RAT is Evolved Universal Terrestrial Radio Access (E-UTRA) orUniversal Terrestrial Radio Access (UTRA); cause transmission of asecond signal to the UE, wherein the second signal indicates that ascaling factor is configured; and receive, from the UE in response toreceipt of the first and second signals, increased carrier monitoringmeasurements.

Example 35 may include the subject matter of Example 34, and may furtherspecify that the increased carrier monitoring measurements includemeasurements of more than four RAT FDD carriers.

Example 36 may include the subject matter of any of Examples 34-35, andmay further specify that: increased carrier monitoring further requiresthe UE to monitor more than four RAT time division duplex (TDD)carriers; and the instructions further cause the eNB to, in response toexecution by the one or more processing devices of the eNB, receivemeasurement from the UE of four or fewer RAT TDD carriers.

Example 37 may include the subject matter of any of Examples 34-36, andmay further specify that increased carrier monitoring requires the UE tomonitor at least eight RAT FDD carriers.

Example 38 may include the subject matter of any of Examples 34-37, andmay further specify that the first signal includes a reduced measurementperformance field of an information element.

Example 39 may include the subject matter of any of Examples 34-38, andmay further specify that the second signal includes a MeasScaleFactorinformation element.

Example 40 may include the subject matter of Example 39, and may furtherspecify that the MeasScaleFactor information element is non-optional.

Example 41 is a method for wireless communication including:configuring, by a user equipment (UE), the UE to support increasedcarrier monitoring, wherein increased carrier monitoring requires the UEto monitor more than four radio access technology (RAT) frequencydivision duplex (FDD) carriers, and wherein the RAT is Evolved UniversalTerrestrial Radio Access (E-UTRA) or Universal Terrestrial Radio Access(UTRA); determining, by the UE, based on one or more signals receivedfrom the eNB, whether a reduced performance group carrier is configured;determining, by the UE, based on the one or more signals received fromthe eNB, whether a scaling factor is configured; and in response to adetermination that no reduced performance group carrier is configuredand a determination that no scaling factor is configured, allowing, bythe UE, the UE to monitor four or fewer RAT FDD carriers.

Example 42 may include the subject matter of Example 41, and may furtherspecify that: increased carrier monitoring further requires the UE tomonitor more than four RAT time division duplex (TDD) carriers; and thatthe method further includes, in response to a determination that noreduced performance group carrier is configured and a determination thatno scaling factor is configured, allowing, by the UE, the UE to monitorfour or fewer RAT TDD carriers.

Example 43 may include the subject matter of any of Examples 41-42, andmay further include, in response to a determination that no reducedperformance group carrier is configured and a determination that ascaling factor is configured, requiring, by the UE, the UE to monitormore than four RAT FDD carriers.

Example 44 may include the subject matter of any of Examples 41-43, andmay further specify that the scaling factor defines a relaxation to beapplied to measurements for reduced performance group carriers.

Example 45 may include the subject matter of Example 44, and may furtherinclude, in response to a determination that one or more reducedperformance group carriers are configured and a determination that ascaling factor is configured, requiring, by the UE, the UE to monitorthe one or more reduced performance group carrier based at least in parton the scaling factor.

Example 46 may include the subject matter of any of Examples 41-45, andmay further specify that increased carrier monitoring requires the UE tomonitor at least eight RAT FDD carriers.

Example 47 may include the subject matter of any of Examples 41-46, andmay further include determining, by the UE, whether a reducedperformance group carrier is configured based on a reduced measurementperformance field of an information element.

Example 48 may include the subject matter of any of Examples 41-47, andmay further include determining, by the UE, whether a scaling factor isconfigured based on a MeasScaleFactor information element.

Example 49 may include the subject matter of any of Examples 41-48, andmay further include operating by the UE, a global positioning systemreceiver.

Example 50 is a method for wireless communication, including:determining, by a user equipment (UE), based on one or more signalsreceived by the UE from an eNB, whether a reduced performance groupcarrier is configured, wherein the UE supports increased carriermonitoring, increased carrier monitoring requires the UE to monitor morethan four frequency division duplex (FDD) carriers; determining, by theUE, based on the one or more signals received from the eNB, whether ascaling factor is configured; and in response to a determination that noreduced performance group carrier is configured and a determination thatno scaling factor is configured, allowing, by the UE, the UE to monitorfour or fewer RAT FDD carriers.

Example 51 may include the subject matter of Example 50, and may furtherspecify that the one or more signals includes a MeasScaleFactorinformation element that indicates that the scaling factor isconfigured.

Example 52 may include the subject matter of any of Examples 50-51, andmay further specify that the scaling factor defines a relaxation to beapplied to measurements for reduced performance group carriers.

Example 53 may include the subject matter of Example 52, and may furtherinclude receiving, by the UE, an additional signal, from the eNB, thatindicates that one or more reduced performance group carriers areconfigured; and providing, by the UE, to the eNB in response to theadditional signal, measurements of the one or more reduced performancegroup carriers made in accordance with the scaling factor.

Example 54 is a method for wireless communication, including: causing,by an eNB, transmission of a first signal to a user equipment (UE),wherein the first signal indicates that no reduced performance groupcarrier is configured, the UE is configured to support increased carriermonitoring, increased carrier monitoring requires the UE to monitor morethan four radio access technology (RAT) frequency division duplex (FDD)carriers, and the RAT is Evolved Universal Terrestrial Radio Access(E-UTRA) or Universal Terrestrial Radio Access (UTRA); causing, by theeNB, transmission of a second signal to the UE, wherein the secondsignal indicates that a scaling factor is configured; and receiving, bythe eNB, from the UE, increased carrier monitoring measurements, whereinthe increased carrier monitoring measurements include measurements ofmore than four RAT FDD carriers, wherein the UE performs the increasedcarrier monitoring measurements in response to receipt of the first andsecond signals.

Example 55 may include the subject matter of Example 54, and may furtherspecify that the second signal includes a MeasScaleFactor informationelement that indicates that a scaling factor is configured.

Example 56 may include the subject matter of any of Examples 54-55, andmay further specify that the scaling factor defines a relaxation to beapplied to measurements for reduced performance group carriers.

Example 57 may include the subject matter of Example 56, and may furtherinclude causing, by the eNB, transmission of a third signal to the UE,wherein the third signal indicates that one or more reduced performancegroup carriers are configured; and receiving, by the eNB, from the UE,in response to the third signal, measurements of the one or more reducedperformance group carriers made in accordance with the scaling factor.

Example 58 may include the subject matter of any of Examples 54-57, andmay further include operating radio hardware, wherein the radio hardwareincludes an antenna.

Example 59 is a method for wireless communication, including: causing,by an eNB, transmission of a first signal to a user equipment (UE),wherein the first signal indicates that no reduced performance groupcarrier is configured, the UE is configured to support increased carriermonitoring, increased carrier monitoring requires the UE to monitor morethan four frequency division duplex (FDD) carriers; causing, by the eNB,transmission of a second signal to the UE, wherein the second signalindicates that a scaling factor is configured; and receiving, by theeNB, from the UE in response to receipt of the first and second signals,increased carrier monitoring measurements.

Example 60 may include the subject matter of Example 59, and may furtherspecify that the increased carrier monitoring measurements includemeasurements of more than four RAT FDD carriers.

Example 61 may include the subject matter of any of Examples 59-60, andmay further specify that: increased carrier monitoring further requiresthe UE to monitor more than four RAT time division duplex (TDD)carriers; and the method further includes receiving, by the eNB,measurement from the UE of four or fewer RAT TDD carriers.

Example 62 may include the subject matter of any of Examples 59-61, andmay further specify that increased carrier monitoring requires the UE tomonitor at least eight RAT FDD carriers.

Example 63 may include the subject matter of any of Examples 59-62, andmay further specify that the first signal includes a reduced measurementperformance field of an information element.

Example 64 may include the subject matter of any of Examples 59-63, andmay further specify that the second signal includes a MeasScaleFactorinformation element.

Example 65 may include the subject matter of Example 64, and may furtherspecify that the MeasScaleFactor information element is non-optional.

Example 66 is a user equipment (UE) for wireless communicationincluding: means for configuring the UE to support increased carriermonitoring, wherein increased carrier monitoring requires the UE tomonitor more than four radio access technology (RAT) frequency divisionduplex (FDD) carriers, and wherein the RAT is Evolved UniversalTerrestrial Radio Access (E-UTRA) or Universal Terrestrial Radio Access(UTRA); means for determining, based on one or more signals receivedfrom the eNB, whether a reduced performance group carrier is configured;determining, by the UE, based on the one or more signals received fromthe eNB, whether a scaling factor is configured; and means for, inresponse to a determination that no reduced performance group carrier isconfigured and a determination that no scaling factor is configured,allowing the UE to monitor four or fewer RAT FDD carriers.

Example 67 may include the subject matter of Example 66, and may furtherspecify that: increased carrier monitoring further requires the UE tomonitor more than four RAT time division duplex (TDD) carriers; and thatthe UE further includes means for, in response to a determination thatno reduced performance group carrier is configured and a determinationthat no scaling factor is configured, allowing the UE to monitor four orfewer RAT TDD carriers.

Example 68 may include the subject matter of any of Examples 66-67, andmay further include means for, in response to a determination that noreduced performance group carrier is configured and a determination thata scaling factor is configured, requiring the UE to monitor more thanfour RAT FDD carriers.

Example 69 may include the subject matter of any of Examples 66-68, andmay further specify that the scaling factor defines a relaxation to beapplied to measurements for reduced performance group carriers.

Example 70 may include the subject matter of Example 69, and may furtherinclude means for, in response to a determination that one or morereduced performance group carriers are configured and a determinationthat a scaling factor is configured, requiring the UE to monitor the oneor more reduced performance group carrier based at least in part on thescaling factor.

Example 71 may include the subject matter of any of Examples 66-70, andmay further specify that increased carrier monitoring requires the UE tomonitor at least eight RAT FDD carriers.

Example 72 may include the subject matter of any of Examples 66-71, andmay further include means for determining whether a reduced performancegroup carrier is configured based on a reduced measurement performancefield of an information element.

Example 73 may include the subject matter of any of Examples 66-72, andmay further include means for determining whether a scaling factor isconfigured based on a MeasScaleFactor information element.

Example 74 may include the subject matter of any of Examples 66-73, andmay further include means for operating a global positioning systemreceiver.

Example 75 is a user equipment (UE), including: means for determiningbased on one or more signals received by the UE from an eNB, whether areduced performance group carrier is configured, wherein the UE supportsincreased carrier monitoring, increased carrier monitoring requires theUE to monitor more than four frequency division duplex (FDD) carriers;means for determining based on the one or more signals received from theeNB, whether a scaling factor is configured; and means for, in responseto a determination that no reduced performance group carrier isconfigured and a determination that no scaling factor is configured,allowing the UE to monitor four or fewer RAT FDD carriers.

Example 76 may include the subject matter of Example 75, and may furtherspecify that the one or more signals includes a MeasScaleFactorinformation element that indicates that the scaling factor isconfigured.

Example 77 may include the subject matter of any of Examples 75-76, andmay further specify that the scaling factor defines a relaxation to beapplied to measurements for reduced performance group carriers.

Example 78 may include the subject matter of Example 77, and may furtherinclude means for receiving an additional signal, from the eNB, thatindicates that one or more reduced performance group carriers areconfigured; and means for providing, to the eNB in response to theadditional signal, measurements of the one or more reduced performancegroup carriers made in accordance with the scaling factor.

Example 79 is an eNB, including: means for causing transmission of afirst signal to a user equipment (UE), wherein the first signalindicates that no reduced performance group carrier is configured, theUE is configured to support increased carrier monitoring, increasedcarrier monitoring requires the UE to monitor more than four radioaccess technology (RAT) frequency division duplex (FDD) carriers, andthe RAT is Evolved Universal Terrestrial Radio Access (E-UTRA) orUniversal Terrestrial Radio Access (UTRA); means for causingtransmission of a second signal to the UE, wherein the second signalindicates that a scaling factor is configured; and means for receiving,from the UE, increased carrier monitoring measurements, wherein theincreased carrier monitoring measurements include measurements of morethan four RAT FDD carriers, wherein the UE performs the increasedcarrier monitoring measurements in response to receipt of the first andsecond signals.

Example 80 may include the subject matter of Example 79, and may furtherspecify that the second signal includes a MeasScaleFactor informationelement that indicates that a scaling factor is configured.

Example 81 may include the subject matter of any of Examples 79-80, andmay further specify that the scaling factor defines a relaxation to beapplied to measurements for reduced performance group carriers.

Example 82 may include the subject matter of Example 81, and may furtherinclude means for causing transmission of a third signal to the UE,wherein the third signal indicates that one or more reduced performancegroup carriers are configured; and means for receiving, from the UE, inresponse to the third signal, measurements of the one or more reducedperformance group carriers made in accordance with the scaling factor.

Example 83 may include the subject matter of any of Examples 79-82, andmay further include means for operating radio hardware, wherein theradio hardware includes an antenna.

Example 84 is an eNB, including: means for causing transmission of afirst signal to a user equipment (UE), wherein the first signalindicates that no reduced performance group carrier is configured, theUE is configured to support increased carrier monitoring, increasedcarrier monitoring requires the UE to monitor more than four frequencydivision duplex (FDD) carriers; means for causing transmission of asecond signal to the UE, wherein the second signal indicates that ascaling factor is configured; and means for receiving, from the UE inresponse to receipt of the first and second signals, increased carriermonitoring measurements.

Example 85 may include the subject matter of Example 84, and may furtherspecify that the increased carrier monitoring measurements includemeasurements of more than four RAT FDD carriers.

Example 86 may include the subject matter of any of Examples 84-85, andmay further specify that: increased carrier monitoring further requiresthe UE to monitor more than four RAT time division duplex (TDD)carriers; and the eNB further includes means for receiving measurementfrom the UE of four or fewer RAT TDD carriers.

Example 87 may include the subject matter of any of Examples 84-86, andmay further specify that increased carrier monitoring requires the UE tomonitor at least eight RAT FDD carriers.

Example 88 may include the subject matter of any of Examples 84-87, andmay further specify that the first signal includes a reduced measurementperformance field of an information element.

Example 89 may include the subject matter of any of Examples 84-88, andmay further specify that the second signal includes a MeasScaleFactorinformation element.

Example 90 may include the subject matter of Example 89, and may furtherspecify that the MeasScaleFactor information element is non-optional.

Example 91 may include an apparatus comprising means to perform theelements of the method or process of any of Examples 1-15 and 41-65, orany other method or process described herein.

Example 92 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform the one or more elements of the method orprocess of any of Examples 1-15 and 41-65, or any other method orprocess described herein.

Example 93 may include an apparatus comprising control circuitry,transmit circuitry, and/or receive circuitry to perform one or moreelements of the method or process of any of Examples 1-15 and 41-65, orany other method or process described herein.

Example 94 may include any of the methods of communicating in a wirelessnetwork shown and described herein.

Example 95 may include any of the systems for providing wirelesscommunication shown and described herein.

Example 96 may include any of the devices for providing wirelesscommunication shown and described herein.

What is claimed is:
 1. One or more non-transitory computer-readablemedia (NTCRM) comprising instructions, wherein execution of theinstructions by one or more processors of a user equipment (UE) is tocause the UE to: determine a measurement performance group to which oneor more carriers belong when an increased UE carrier monitoringUniversal Mobile Telecommunications System (UMTS) Terrestrial RadioAccess (UTRA) capability is supported or when an increased UE carriermonitoring Evolved UMTS Terrestrial Radio Access (E-UTRA) capability issupported, wherein the measurement performance group is a normalperformance group or a reduced performance group, wherein carriersbelonging to the normal performance group have a better delayperformance compared to a delay performance of carriers belonging to thereduced performance group; and at least one of: consider each of the oneor more carriers as belonging to the normal performance group when noreduced performance group carrier is configured; or when no measurementscaling factor is configured, monitor at least a number of the one ormore carriers according to a legacy carrier monitoring capability and isnot required to monitor an increased number of carriers according to theincreased UE carrier monitoring UTRA capability or the increased UEcarrier monitoring E-UTRA capability.
 2. The one or more NTCRM of claim1, wherein execution of the instructions is to cause the UE to: considerat least one of the one or more carriers as belonging to the reducedperformance group when at least one reduced performance group carrier isconfigured.
 3. The one or more NTCRM of claim 2, wherein execution ofthe instructions is to cause the UE to: determine that no reducedperformance group carrier is configured when a reduced measurementperformance (reducedMeasPerformance) field is not included in a radioresource control (RRC) message; and determine that at least one reducedperformance group carrier is configured when the reducedMeasPerformancefield is included in the RRC message and has a value of ‘true’.
 4. Theone or more NTCRM of claim 3, wherein the reducedMeasPerformance fieldis included in a measurement configuration (MeasConfig) informationelement (IE) of the RRC message.
 5. The one or more NTCRM of claim 3,wherein the reducedMeasPerformance field is included in a systeminformation block (SIB) of the RRC message.
 6. The one or more NTCRM ofclaim 5, wherein execution of the instructions is to cause the UE to:identify the SIB included in the obtained RRC message, wherein the SIBis to include information about E-UTRA frequencies or UTRA frequenciesand inter-frequency neighboring cells relevant for cell re-selection;and for each listed E-UTRA or UTRA frequency carrier or each listedinter-frequency carrier: determine that a carrier frequency of theinter-frequency carrier or the E-UTRA or UTRA frequency is configuredfor reduced measurement performance when a value of ‘true’ is includedin a reducedMeasPerformance field of the inter-frequency carrier or theE-UTRA or UTRA frequency, and determine that the carrier frequency ofthe inter-frequency carrier or the E-UTRA or UTRA frequency isconfigured for normal measurement performance when thereducedMeasPerformance field is not included in the SIB.
 7. The one ormore NTCRM of claim 1, wherein execution of the instructions is to causethe UE to: determine whether the measurement scaling factor is includedin a measurement scaling factor (measScaleFactor) IE, wherein themeasScaleFactor IE is included in a MeasConfig IE of an obtained RRCmessage.
 8. The one or more NTCRM of claim 7, wherein themeasScaleFactor IE comprises a setting of 8 or
 16. 9. The one or moreNTCRM of claim 7, wherein execution of the instructions is to cause theUE to: identify a list of measurement objects indicated by theMeasConfig IE; and monitor carriers indicated by each of the listedmeasurement objects.
 10. The one or more NTCRM of claim 9, whereinexecution of the instructions is to cause the UE to: for each listedmeasurement object: determine that a carrier indicated by themeasurement object is configured for reduced measurement performancewhen a value of ‘true’ is included in a reducedMeasPerformance field ofthe measurement object; and determine that the carrier indicated by themeasurement object is configured for normal measurement performance whenthe measurement object does not include the reducedMeasPerformancefield.
 11. A system on chip (SoC) to be implemented in a user equipment(UE), the SoC comprising: baseband circuitry with on-board memorycircuitry, the baseband circuitry to: determine a measurementperformance group to which one or more carriers belong when an increasedUE carrier monitoring Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access (UTRA) capability is supported or when anincreased UE carrier monitoring Evolved UMTS Terrestrial Radio Access(E-UTRA) capability is supported, wherein the measurement performancegroup is a normal performance group or a reduced performance group,wherein carriers belonging to the normal performance group have a betterdelay performance compared to a delay performance of carriers belongingto the reduced performance group; consider each of the one or morecarriers as belonging to the normal performance group when no reducedperformance group carrier is configured; and when no measurement scalingfactor is configured, monitor at least a number of the one or morecarriers according to a legacy carrier monitoring capability and is notrequired to monitor an increased number of carriers according to theincreased UE carrier monitoring UTRA capability or the increased UEcarrier monitoring E-UTRA capability.
 12. The SoC of claim 11, whereinthe baseband circuitry is to: consider at least one of the one or morecarriers as belonging to the reduced performance group when at least onereduced performance group carrier is configured.
 13. The SoC of claim11, wherein the baseband circuitry is to: determine that no reducedperformance group carrier is configured when a reduced measurementperformance (reducedMeasPerformance) field is not included in a radioresource control (RRC) message; and determine that at least one reducedperformance group carrier is configured when the reducedMeasPerformancefield is included in the RRC message and has a value of ‘true’.
 14. TheSoC of claim 11, wherein the reducedMeasPerformance field is included ina measurement configuration (MeasConfig) information element (IE) of theRRC message.
 15. The SoC of claim 14, wherein the reducedMeasPerformancefield is included in a system information block (SIB) of the RRCmessage.
 16. The SoC of claim 15, wherein the baseband circuitry is to:identify the SIB included in the obtained RRC message, wherein the SIBis to include information about E-UTRA frequencies or UTRA frequenciesand inter-frequency neighboring cells relevant for cell re-selection;and for each listed E-UTRA or UTRA frequency carrier or each listedinter-frequency carrier: determine that a carrier frequency of theinter-frequency carrier or the E-UTRA or UTRA frequency is configuredfor reduced measurement performance when a value of ‘true’ is includedin a reducedMeasPerformance field of the inter-frequency carrier or theE-UTRA or UTRA frequency, and determine that the carrier frequency ofthe inter-frequency carrier or the E-UTRA or UTRA frequency isconfigured for normal measurement performance when thereducedMeasPerformance field is not included in the SIB.
 17. The SoC ofclaim 11, wherein the baseband circuitry is to: determine whether themeasurement scaling factor is included in a measurement scaling factor(measScaleFactor) IE, wherein the measScaleFactor IE is included in aMeasConfig IE of an obtained RRC message.
 18. The SoC of claim 17,wherein the measScaleFactor IE comprises a setting of 8 or
 16. 19. TheSoC of claim 18, wherein the baseband circuitry is to: identify a listof measurement objects indicated by the MeasConfig 1E; and monitorcarriers indicated by each of the listed measurement objects.
 20. TheSoC of claim 19, wherein the baseband circuitry is to: for each listedmeasurement object: determine that a carrier indicated by themeasurement object is configured for reduced measurement performancewhen a value of ‘true’ is included in a reducedMeasPerformance field ofthe measurement object; and determine that the carrier indicated by themeasurement object is configured for normal measurement performance whenthe measurement object does not include the reducedMeasPerformancefield.
 21. An apparatus to be employed as an evolved NodeB (eNB), theapparatus comprising: processor circuitry to: determine a measurementperformance group to which one or more carriers belong when a userequipment (UE) indicates support for an increased UE carrier monitoringUniversal Mobile Telecommunications System (UMTS) Terrestrial RadioAccess (UTRA) capability is supported or support for an increased UEcarrier monitoring Evolved UMTS Terrestrial Radio Access (E-UTRA)capability, wherein the measurement performance group is a normalperformance group or a reduced performance group, wherein carriersbelonging to the normal performance group have a better delayperformance compared to a delay performance of carriers belonging to thereduced performance group, generate a configuration message to notindicate a reduced performance group carrier when the one or morecarriers belong to the normal performance group, and generate theconfiguration message to not include a measurement scaling factor whenthe UE is determined to monitor at least a number of the one or morecarriers according to a legacy carrier monitoring capability and is notrequired to monitor an increased number of carriers according to theincreased UE carrier monitoring UTRA capability or the increased UEcarrier monitoring E-UTRA capability; and communication circuitrycoupled with the processor circuitry, the communication circuitry tocontrol transmission of the generated message to the UE.
 22. Theapparatus of claim 21, wherein the configuration message is a radioresource control (RRC) message, and the processor circuitry is to:generate the RRC message to not include a reduced measurementperformance (reducedMeasPerformance) field when no reduced performancegroup carrier is to be configured for the UE; and generate the RRCmessage to include a reducedMeasPerformance field with a value of ‘true’when at least one reduced performance group carrier is to be configuredfor the UE.
 23. The apparatus of claim 22, wherein thereducedMeasPerformance field is included in a measurement configuration(MeasConfig) information element (IE) of the RRC message.
 24. Theapparatus of claim 22, wherein the reducedMeasPerformance field isincluded in a system information block (SIB) of the RRC message.
 25. Theapparatus of claim 21, wherein the processor circuitry is to: generatethe RRC message to not include a measurement scaling factor(measScaleFactor) IE when the UE is determined to monitor at least anumber of the one or more carriers according to a legacy carriermonitoring capability; and generate the RRC message to include themeasurement scaling factor in a measurement scaling factor(measScaleFactor) IE in a MeasConfig IE of the RRC message when the UEis determined to be required to monitor an increased number of carriersaccording to the increased UE carrier monitoring UTRA capability or theincreased UE carrier monitoring E-UTRA capability.